-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Add 'Additional Notes' for NTLM Block error #6916
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
When the certificate replacement is executed by an account that is member of 'Protected Users', the NTLM authentication is blocked (and it's used by the replacement). This is documented in the Protected Users page, but not in the certificate replacement page. Currently, the only occurrence of the scenario is under a forum post. Updating here because it would have saved me 3 days of troubleshooting in a recent case, and may save others :)
@vbrennydossa : Thanks for your contribution! The author(s) have been notified to review your proposed change. @jenfieldmsft |
Learn Build status updates of commit 79ec54e: ✅ Validation status: passed
For more details, please refer to the build report. Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report. For any questions, please:
|
#assign: @robinharwood, @Xelu86 Can you review the proposed changes? New content should be submitted via the private repo to benefit from staging, validation, and Acrolinx checks. Let us know if you'd like assistance with moving the commits into the private repo. #label:"aq-pr-triaged" |
The following users don't have valid GitHub IDs, or are not collaborators on this repo: robinharwood xelu86 |
Freshness pass: Group Policy overview
When the certificate replacement is executed by an account that is member of 'Protected Users', the NTLM authentication is blocked (and it's used by the replacement). This is documented in the Protected Users page, but not in the certificate replacement page. Currently, the only occurrence of the scenario is under a forum post. Updating here because it would have saved me 3 days of troubleshooting in a recent case, and may save others :)